Transmitting a power headroom report for a primary cell

ABSTRACT

A wireless device receives a first parameter indicating that simultaneous physical uplink control channel (PUCCH) and physical uplink shared channel (PUSCH) transmission is not configured for a primary cell of a plurality of cells. The plurality of cells comprise the primary cell and a PUCCH secondary cell. Based on the PUCCH secondary cell being activated, the wireless device transmits a PH report comprising a first Type 2 PH field for the primary cell while the simultaneous PUCCH and PUSCH transmission is not configured for the primary cell.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.16/259,836, filed Jan. 28, 2019, which is a continuation of U.S. patentapplication Ser. No. 15/233,237, filed Aug. 10, 2016, (now U.S. Pat. No.10,194,406, issued Oct. 2, 2018), which claims the benefit of U.S.Provisional Application No. 62/234,922, filed Sep. 30, 2015, which ishereby incorporated by reference in its entirety.

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS

Examples of several of the various embodiments of the present inventionare described herein with reference to the drawings.

FIG. 1 is a diagram depicting example sets of OFDM subcarriers as per anaspect of an embodiment of the present invention.

FIG. 2 is a diagram depicting an example transmission time and receptiontime for two carriers in a carrier group as per an aspect of anembodiment of the present invention.

FIG. 3 is a diagram depicting OFDM radio resources as per an aspect ofan embodiment of the present invention.

FIG. 4 is a block diagram of a base station and a wireless device as peran aspect of an embodiment of the present invention.

FIG. 5A, FIG. 5B, FIG. 5C and FIG. 5D are example diagrams for uplinkand downlink signal transmission as per an aspect of an embodiment ofthe present invention.

FIG. 6 is an example diagram for a protocol structure with CA and DC asper an aspect of an embodiment of the present invention.

FIG. 7 is an example diagram for a protocol structure with CA and DC asper an aspect of an embodiment of the present invention.

FIG. 8 shows example TAG configurations as per an aspect of anembodiment of the present invention.

FIG. 9 is an example message flow in a random access process in asecondary TAG as per an aspect of an embodiment of the presentinvention.

FIG. 10 is an example grouping of cells into PUCCH groups as per anaspect of an embodiment of the present invention.

FIG. 11 illustrates example groupings of cells into one or more PUCCHgroups and one or more TAGs as per an aspect of an embodiment of thepresent invention.

FIG. 12 illustrates example groupings of cells into one or more PUCCHgroups and one or more TAGs as per an aspect of an embodiment of thepresent invention.

FIG. 13 is an example MAC PDU as per an aspect of an embodiment of thepresent invention.

FIG. 14 is an example flow diagram as per an aspect of an embodiment ofthe present invention.

FIG. 15 is an example flow diagram as per an aspect of an embodiment ofthe present invention.

DETAILED DESCRIPTION OF EMBODIMENTS

Example embodiments of the present invention enable operation ofmultiple physical uplink control channel (PUCCH) groups. Embodiments ofthe technology disclosed herein may be employed in the technical fieldof multicarrier communication systems. More particularly, theembodiments of the technology disclosed herein may relate to operationof PUCCH groups.

The following Acronyms are used throughout the present disclosure:

ASIC application-specific integrated circuit

BPSK binary phase shift keying

CA carrier aggregation

CSI channel state information

CDMA code division multiple access

CSS common search space

CPLD complex programmable logic devices

CC component carrier

DL downlink

DCI downlink control information

DC dual connectivity

EPC evolved packet core

E-UTRAN evolved-universal terrestrial radio access network

FPGA field programmable gate arrays

FDD frequency division multiplexing

HDL hardware description languages

HARQ hybrid automatic repeat request

IE information element

LTE long term evolution

MCG master cell group

MeNB master evolved node B

MIB master information block

MAC media access control

MAC media access control

MME mobility management entity

NAS non-access stratum

OFDM orthogonal frequency division multiplexing

PDCP packet data convergence protocol

PDU packet data unit

PHY physical

PDCCH physical downlink control channel

PHICH physical HARQ indicator channel

PUCCH physical uplink control channel

PUSCH physical uplink shared channel

PCell primary cell

PCell primary cell

PCC primary component carrier

PSCell primary secondary cell

pTAG primary timing advance group

QAM quadrature amplitude modulation

QPSK quadrature phase shift keying

RBG Resource Block Groups

RLC radio link control

RRC radio resource control

RA random access

RB resource blocks

SCC secondary component carrier

SCell secondary cell

Scell secondary cells

SCG secondary cell group

SeNB secondary evolved node B

sTAGs secondary timing advance group

SDU service data unit

S-GW serving gateway

SRB signaling radio bearer

SC-OFDM single carrier-OFDM

SFN system frame number

SIB system information block

TAI tracking area identifier

TAT time alignment timer

TDD time division duplexing

TDMA time division multiple access

TA timing advance

TAG timing advance group

TB transport block

UL uplink

UE user equipment

VHDL VHSIC hardware description language

Example embodiments of the invention may be implemented using variousphysical layer modulation and transmission mechanisms. Exampletransmission mechanisms may include, but are not limited to: CDMA, OFDM,TDMA, Wavelet technologies, and/or the like. Hybrid transmissionmechanisms such as TDMA/CDMA, and OFDM/CDMA may also be employed.Various modulation schemes may be applied for signal transmission in thephysical layer. Examples of modulation schemes include, but are notlimited to: phase, amplitude, code, a combination of these, and/or thelike. An example radio transmission method may implement QAM using BPSK,QPSK, 16-QAM, 64-QAM, 256-QAM, and/or the like. Physical radiotransmission may be enhanced by dynamically or semi-dynamically changingthe modulation and coding scheme depending on transmission requirementsand radio conditions.

FIG. 1 is a diagram depicting example sets of OFDM subcarriers as per anaspect of an embodiment of the present invention. As illustrated in thisexample, arrow(s) in the diagram may depict a subcarrier in amulticarrier OFDM system. The OFDM system may use technology such asOFDM technology, SC-OFDM technology, or the like. For example, arrow 101shows a subcarrier transmitting information symbols. FIG. 1 is forillustration purposes, and a typical multicarrier OFDM system mayinclude more subcarriers in a carrier. For example, the number ofsubcarriers in a carrier may be in the range of 10 to 10,000subcarriers. FIG. 1 shows two guard bands 106 and 107 in a transmissionband. As illustrated in FIG. 1, guard band 106 is between subcarriers103 and subcarriers 104. The example set of subcarriers A 102 includessubcarriers 103 and subcarriers 104. FIG. 1 also illustrates an exampleset of subcarriers B 105. As illustrated, there is no guard band betweenany two subcarriers in the example set of subcarriers B 105. Carriers ina multicarrier OFDM communication system may be contiguous carriers,non-contiguous carriers, or a combination of both contiguous andnon-contiguous carriers.

FIG. 2 is a diagram depicting an example transmission time and receptiontime for two carriers as per an aspect of an embodiment of the presentinvention. A multicarrier OFDM communication system may include one ormore carriers, for example, ranging from 1 to 10 carriers. Carrier A 204and carrier B 205 may have the same or different timing structures.Although FIG. 2 shows two synchronized carriers, carrier A 204 andcarrier B 205 may or may not be synchronized with each other. Differentradio frame structures may be supported for FDD and TDD duplexmechanisms. FIG. 2 shows an example FDD frame timing. Downlink anduplink transmissions may be organized into radio frames 201. In thisexample, radio frame duration is 10 msec. Other frame durations, forexample, in the range of 1 to 100 msec may also be supported. In thisexample, each 10 ms radio frame 201 may be divided into ten equallysized subframes 202. Other subframe durations such as including 0.5msec, 1 msec, 2 msec, and 5 msec may also be supported. Subframe(s) mayconsist of two or more slots (e.g. slots 206 and 207). For the exampleof FDD, 10 subframes may be available for downlink transmission and 10subframes may be available for uplink transmissions in each 10 msinterval. Uplink and downlink transmissions may be separated in thefrequency domain. Slot(s) may include a plurality of OFDM symbols 203.The number of OFDM symbols 203 in a slot 206 may depend on the cyclicprefix length and subcarrier spacing.

FIG. 3 is a diagram depicting OFDM radio resources as per an aspect ofan embodiment of the present invention. The resource grid structure intime 304 and frequency 305 is illustrated in FIG. 3. The quantity ofdownlink subcarriers or RBs (in this example 6 to 100 RBs) may depend,at least in part, on the downlink transmission bandwidth 306 configuredin the cell. The smallest radio resource unit may be called a resourceelement (e.g. 301). Resource elements may be grouped into resourceblocks (e.g. 302). Resource blocks may be grouped into larger radioresources called Resource Block Groups (RBG) (e.g. 303). The transmittedsignal in slot 206 may be described by one or several resource grids ofa plurality of subcarriers and a plurality of OFDM symbols. Resourceblocks may be used to describe the mapping of certain physical channelsto resource elements. Other pre-defined groupings of physical resourceelements may be implemented in the system depending on the radiotechnology. For example, 24 subcarriers may be grouped as a radio blockfor a duration of 5 msec. In an illustrative example, a resource blockmay correspond to one slot in the time domain and 180 kHz in thefrequency domain (for 15 KHz subcarrier bandwidth and 12 subcarriers).

FIG. 5A, FIG. 5B, FIG. 5C and FIG. 5D are example diagrams for uplinkand downlink signal transmission as per an aspect of an embodiment ofthe present invention. FIG. 5A shows an example uplink physical channel.The baseband signal representing the physical uplink shared channel mayperform the following processes. These functions are illustrated asexamples and it is anticipated that other mechanisms may be implementedin various embodiments. The functions may comprise scrambling,modulation of scrambled bits to generate complex-valued symbols, mappingof the complex-valued modulation symbols onto one or severaltransmission layers, transform precoding to generate complex-valuedsymbols, precoding of the complex-valued symbols, mapping of precodedcomplex-valued symbols to resource elements, generation ofcomplex-valued time-domain SC-FDMA signal for each antenna port, and/orthe like.

Example modulation and up-conversion to the carrier frequency of thecomplex-valued SC-FDMA baseband signal for each antenna port and/or thecomplex-valued PRACH baseband signal is shown in FIG. 5B. Filtering maybe employed prior to transmission.

An example structure for Downlink Transmissions is shown in FIG. 5C. Thebaseband signal representing a downlink physical channel may perform thefollowing processes. These functions are illustrated as examples and itis anticipated that other mechanisms may be implemented in variousembodiments. The functions include scrambling of coded bits in each ofthe codewords to be transmitted on a physical channel; modulation ofscrambled bits to generate complex-valued modulation symbols; mapping ofthe complex-valued modulation symbols onto one or several transmissionlayers; precoding of the complex-valued modulation symbols on each layerfor transmission on the antenna ports; mapping of complex-valuedmodulation symbols for each antenna port to resource elements;generation of complex-valued time-domain OFDM signal for each antennaport, and/or the like.

Example modulation and up-conversion to the carrier frequency of thecomplex-valued OFDM baseband signal for each antenna port is shown inFIG. 5D. Filtering may be employed prior to transmission.

FIG. 4 is an example block diagram of a base station 401 and a wirelessdevice 406, as per an aspect of an embodiment of the present invention.A communication network 400 may include at least one base station 401and at least one wireless device 406. The base station 401 may includeat least one communication interface 402, at least one processor 403,and at least one set of program code instructions 405 stored innon-transitory memory 404 and executable by the at least one processor403. The wireless device 406 may include at least one communicationinterface 407, at least one processor 408, and at least one set ofprogram code instructions 410 stored in non-transitory memory 409 andexecutable by the at least one processor 408. Communication interface402 in base station 401 may be configured to engage in communicationwith communication interface 407 in wireless device 406 via acommunication path that includes at least one wireless link 411.Wireless link 411 may be a bi-directional link. Communication interface407 in wireless device 406 may also be configured to engage in acommunication with communication interface 402 in base station 401. Basestation 401 and wireless device 406 may be configured to send andreceive data over wireless link 411 using multiple frequency carriers.According to some of the various aspects of embodiments, transceiver(s)may be employed. A transceiver is a device that includes both atransmitter and receiver. Transceivers may be employed in devices suchas wireless devices, base stations, relay nodes, and/or the like.Example embodiments for radio technology implemented in communicationinterface 402, 407 and wireless link 411 are illustrated are FIG. 1,FIG. 2, FIG. 3, FIG. 5, and associated text.

An interface may be a hardware interface, a firmware interface, asoftware interface, and/or a combination thereof. The hardware interfacemay include connectors, wires, electronic devices such as drivers,amplifiers, and/or the like. A software interface may include codestored in a memory device to implement protocol(s), protocol layers,communication drivers, device drivers, combinations thereof, and/or thelike. A firmware interface may include a combination of embeddedhardware and code stored in and/or in communication with a memory deviceto implement connections, electronic device operations, protocol(s),protocol layers, communication drivers, device drivers, hardwareoperations, combinations thereof, and/or the like.

The term configured may relate to the capacity of a device whether thedevice is in an operational or non-operational state. Configured mayalso refer to specific settings in a device that effect the operationalcharacteristics of the device whether the device is in an operational ornon-operational state. In other words, the hardware, software, firmware,registers, memory values, and/or the like may be “configured” within adevice, whether the device is in an operational or nonoperational state,to provide the device with specific characteristics. Terms such as “acontrol message to cause in a device” may mean that a control messagehas parameters that may be used to configure specific characteristics inthe device, whether the device is in an operational or non-operationalstate.

According to some of the various aspects of embodiments, an LTE networkmay include a multitude of base stations, providing a user planePDCP/RLC/MAC/PHY and control plane (RRC) protocol terminations towardsthe wireless device. The base station(s) may be interconnected withother base station(s) (e.g. employing an X2 interface). The basestations may also be connected employing, for example, an S1 interfaceto an EPC. For example, the base stations may be interconnected to theMME employing the S1-MME interface and to the S-G) employing the S1-Uinterface. The S1 interface may support a many-to-many relation betweenMMEs/Serving Gateways and base stations. A base station may include manysectors for example: 1, 2, 3, 4, or 6 sectors. A base station mayinclude many cells, for example, ranging from 1 to 50 cells or more. Acell may be categorized, for example, as a primary cell or secondarycell. At RRC connection establishment/re-establishment/handover, oneserving cell may provide the NAS (non-access stratum) mobilityinformation (e.g. TAI), and at RRC connection re-establishment/handover,one serving cell may provide the security input. This cell may bereferred to as the Primary Cell (PCell). In the downlink, the carriercorresponding to the PCell may be the Downlink Primary Component Carrier(DL PCC), while in the uplink, it may be the Uplink Primary ComponentCarrier (UL PCC). Depending on wireless device capabilities, SecondaryCells (SCells) may be configured to form together with the PCell a setof serving cells. In the downlink, the carrier corresponding to an SCellmay be a Downlink Secondary Component Carrier (DL SCC), while in theuplink, it may be an Uplink Secondary Component Carrier (UL SCC). AnSCell may or may not have an uplink carrier.

A cell, comprising a downlink carrier and optionally an uplink carrier,may be assigned a physical cell ID and a cell index. A carrier (downlinkor uplink) may belong to only one cell. The cell ID or Cell index mayalso identify the downlink carrier or uplink carrier of the cell(depending on the context it is used). In the specification, cell ID maybe equally referred to a carrier ID, and cell index may be referred tocarrier index. In implementation, the physical cell ID or cell index maybe assigned to a cell. A cell ID may be determined using asynchronization signal transmitted on a downlink carrier. A cell indexmay be determined using RRC messages. For example, when thespecification refers to a first physical cell ID for a first downlinkcarrier, the specification may mean the first physical cell ID is for acell comprising the first downlink carrier. The same concept may applyto, for example, carrier activation. When the specification indicatesthat a first carrier is activated, the specification may equally meanthat the cell comprising the first carrier is activated.

Embodiments may be configured to operate as needed. The disclosedmechanism may be performed when certain criteria are met, for example,in a wireless device, a base station, a radio environment, a network, acombination of the above, and/or the like. Example criteria may bebased, at least in part, on for example, traffic load, initial systemset up, packet sizes, traffic characteristics, a combination of theabove, and/or the like. When the one or more criteria are met, variousexample embodiments may be applied. Therefore, it may be possible toimplement example embodiments that selectively implement disclosedprotocols.

A base station may communicate with a mix of wireless devices. Wirelessdevices may support multiple technologies, and/or multiple releases ofthe same technology. Wireless devices may have some specificcapability(ies) depending on its wireless device category and/orcapability(ies). A base station may comprise multiple sectors. When thisdisclosure refers to a base station communicating with a plurality ofwireless devices, this disclosure may refer to a subset of the totalwireless devices in a coverage area. This disclosure may refer to, forexample, a plurality of wireless devices of a given LTE release with agiven capability and in a given sector of the base station. Theplurality of wireless devices in this disclosure may refer to a selectedplurality of wireless devices, and/or a subset of total wireless devicesin a coverage area which perform according to disclosed methods, and/orthe like. There may be a plurality of wireless devices in a coveragearea that may not comply with the disclosed methods, for example,because those wireless devices perform based on older releases of LTEtechnology.

FIG. 6 and FIG. 7 are example diagrams for protocol structure with CAand DC as per an aspect of an embodiment of the present invention.E-UTRAN may support Dual Connectivity (DC) operation whereby a multipleRX/TX UE in RRC_CONNECTED may be configured to utilize radio resourcesprovided by two schedulers located in two eNBs connected via a non-idealbackhaul over the X2 interface. eNBs involved in DC for a certain UE mayassume two different roles: an eNB may either act as an MeNB or as anSeNB. In DC a UE may be connected to one MeNB and one SeNB. Mechanismsimplemented in DC may be extended to cover more than two eNBs. FIG. 7illustrates one example structure for the UE side MAC entities when aMaster Cell Group (MCG) and a Secondary Cell Group (SCG) are configured,and it may not restrict implementation. Media Broadcast MulticastService (MBMS) reception is not shown in this figure for simplicity.

In DC, the radio protocol architecture that a particular bearer uses maydepend on how the bearer is setup. Three alternatives may exist, an MCGbearer, an SCG bearer and a split bearer as shown in FIG. 6. RRC may belocated in MeNB and SRBs may be configured as a MCG bearer type and mayuse the radio resources of the MeNB. DC may also be described as havingat least one bearer configured to use radio resources provided by theSeNB. DC may or may not be configured/implemented in example embodimentsof the invention.

In the case of DC, the UE may be configured with two MAC entities: oneMAC entity for MeNB, and one MAC entity for SeNB. In DC, the configuredset of serving cells for a UE may comprise of two subsets: the MasterCell Group (MCG) containing the serving cells of the MeNB, and theSecondary Cell Group (SCG) containing the serving cells of the SeNB. Fora SCG, one or more of the following may be applied: at least one cell inthe SCG has a configured UL CC and one of them, named PSCell (or PCellof SCG, or sometimes called PCell), is configured with PUCCH resources;when the SCG is configured, there may be at least one SCG bearer or oneSplit bearer; upon detection of a physical layer problem or a randomaccess problem on a PSCell, or the maximum number of RLC retransmissionshas been reached associated with the SCG, or upon detection of an accessproblem on a PSCell during a SCG addition or a SCG change: a RRCconnection re-establishment procedure may not be triggered, ULtransmissions towards cells of the SCG are stopped, a MeNB may beinformed by the UE of a SCG failure type, for split bearer, the DL datatransfer over the MeNB is maintained; the RLC AM bearer may beconfigured for the split bearer; like PCell, PSCell may not bede-activated; PSCell may be changed with a SCG change (e.g. withsecurity key change and a RACH procedure); and/or neither a directbearer type change between a Split bearer and a SCG bearer norsimultaneous configuration of a SCG and a Split bearer are supported.

With respect to the interaction between a MeNB and a SeNB, one or moreof the following principles may be applied: the MeNB may maintain theRRM measurement configuration of the UE and may, (e.g., based onreceived measurement reports or traffic conditions or bearer types),decide to ask a SeNB to provide additional resources (serving cells) fora UE; upon receiving a request from the MeNB, a SeNB may create acontainer that may result in the configuration of additional servingcells for the UE (or decide that it has no resource available to do so);for UE capability coordination, the MeNB may provide (part of) the ASconfiguration and the UE capabilities to the SeNB; the MeNB and the SeNBmay exchange information about a UE configuration by employing of RRCcontainers (inter-node messages) carried in X2 messages; the SeNB mayinitiate a reconfiguration of its existing serving cells (e.g., PUCCHtowards the SeNB); the SeNB may decide which cell is the PSCell withinthe SCG; the MeNB may not change the content of the RRC configurationprovided by the SeNB; in the case of a SCG addition and a SCG SCelladdition, the MeNB may provide the latest measurement results for theSCG cell(s); both a MeNB and a SeNB may know the SFN and subframe offsetof each other by OAM, (e.g., for the purpose of DRX alignment andidentification of a measurement gap). In an example, when adding a newSCG SCell, dedicated RRC signaling may be used for sending requiredsystem information of the cell as for CA, except for the SFN acquiredfrom a MIB of the PSCell of a SCG.

According to some of the various aspects of embodiments, serving cellshaving an uplink to which the same time alignment (TA) applies may begrouped in a TA group (TAG). Serving cells in one TAG may use the sametiming reference. For a given TAG, user equipment (UE) may use onedownlink carrier as a timing reference at a given time. The UE may use adownlink carrier in a TAG as a timing reference for that TAG. For agiven TAG, a UE may synchronize uplink subframe and frame transmissiontiming of uplink carriers belonging to the same TAG. According to someof the various aspects of embodiments, serving cells having an uplink towhich the same TA applies may correspond to serving cells hosted by thesame receiver. A TA group may comprise at least one serving cell with aconfigured uplink. A UE supporting multiple TAs may support two or moreTA groups. One TA group may contain the PCell and may be called aprimary TAG (pTAG). In a multiple TAG configuration, at least one TAgroup may not contain the PCell and may be called a secondary TAG(sTAG). Carriers within the same TA group may use the same TA value andthe same timing reference. When DC is configured, cells belonging to acell group (MCG or SCG) may be grouped into multiple TAGs including apTAG and one or more sTAGs.

FIG. 8 shows example TAG configurations as per an aspect of anembodiment of the present invention. In Example 1, pTAG comprises PCell,and an sTAG comprises SCell1. In Example 2, a pTAG comprises a PCell andSCell1, and an sTAG comprises SCell2 and SCell3. In Example 3, pTAGcomprises PCell and SCell1, and an sTAG1 includes SCell2 and SCell3, andsTAG2 comprises SCell4. Up to four TAGs may be supported in a cell group(MCG or SCG) and other example TAG configurations may also be provided.In various examples in this disclosure, example mechanisms are describedfor a pTAG and an sTAG. The operation with one example sTAG isdescribed, and the same operation may be applicable to other sTAGs. Theexample mechanisms may be applied to configurations with multiple sTAGs.

According to some of the various aspects of embodiments, TA maintenance,pathloss reference handling and a timing reference for a pTAG may followLTE release 10 principles in the MCG and/or SCG. The UE may need tomeasure downlink pathloss to calculate uplink transmit power. A pathlossreference may be used for uplink power control and/or transmission ofrandom access preamble(s). UE may measure downlink pathloss usingsignals received on a pathloss reference cell. For SCell(s) in a pTAG,the choice of a pathloss reference for cells may be selected from and/orbe limited to the following two options: a) the downlink SCell linked toan uplink SCell using system information block 2 (SIB2), and b) thedownlink pCell. The pathloss reference for SCells in a pTAG may beconfigurable using RRC message(s) as a part of an SCell initialconfiguration and/or reconfiguration. According to some of the variousaspects of embodiments, a PhysicalConfigDedicatedSCell informationelement (IE) of an SCell configuration may include a pathloss referenceSCell (downlink carrier) for an SCell in a pTAG. The downlink SCelllinked to an uplink SCell using system information block 2 (SIB2) may bereferred to as the SIB2 linked downlink of the SCell. Different TAGs mayoperate in different bands. For an uplink carrier in an sTAG, thepathloss reference may be only configurable to the downlink SCell linkedto an uplink SCell using the system information block 2 (SIB2) of theSCell.

To obtain initial uplink (UL) time alignment for an sTAG, an eNB mayinitiate an RA procedure. In an sTAG, a UE may use one of any activatedSCells from this sTAG as a timing reference cell. In an exampleembodiment, the timing reference for SCells in an sTAG may be the SIB2linked downlink of the SCell on which the preamble for the latest RAprocedure was sent. There may be one timing reference and one timealignment timer (TAT) per TA group. A TAT for TAGs may be configuredwith different values. In a MAC entity, when a TAT associated with apTAG expires: all TATs may be considered as expired, the UE may flushHARQ buffers of serving cells, the UE may clear any configured downlinkassignment/uplink grants, and the RRC in the UE may release PUCCH/SRSfor all configured serving cells. When the pTAG TAT is not running, ansTAG TAT may not be running. When the TAT associated with an sTAGexpires: a) SRS transmissions may be stopped on the correspondingSCells, b) SRS RRC configuration may be released, c) CSI reportingconfiguration for corresponding SCells may be maintained, and/or d) theMAC in the UE may flush the uplink HARQ buffers of the correspondingSCells.

An eNB may initiate an RA procedure via a PDCCH order for an activatedSCell. This PDCCH order may be sent on a scheduling cell of this SCell.When cross carrier scheduling is configured for a cell, the schedulingcell may be different than the cell that is employed for preambletransmission, and the PDCCH order may include an SCell index. At least anon-contention based RA procedure may be supported for SCell(s) assignedto sTAG(s).

FIG. 9 is an example message flow in a random access process in asecondary TAG as per an aspect of an embodiment of the presentinvention. An eNB transmits an activation command 600 to activate anSCell. A preamble 602 (Msg1) may be sent by a UE in response to a PDCCHorder 601 on an SCell belonging to an sTAG. In an example embodiment,preamble transmission for SCells may be controlled by the network usingPDCCH format 1A. Msg2 message 603 (RAR: random access response) inresponse to the preamble transmission on the SCell may be addressed toRA-RNTI in a PCell common search space (CSS). Uplink packets 604 may betransmitted on the SCell in which the preamble was transmitted.

According to some of the various aspects of embodiments, initial timingalignment may be achieved through a random access procedure. This mayinvolve a UE transmitting a random access preamble and an eNB respondingwith an initial TA command NTA (amount of timing advance) within arandom access response window. The start of the random access preamblemay be aligned with the start of a corresponding uplink subframe at theUE assuming NTA=0. The eNB may estimate the uplink timing from therandom access preamble transmitted by the UE. The TA command may bederived by the eNB based on the estimation of the difference between thedesired UL timing and the actual UL timing. The UE may determine theinitial uplink transmission timing relative to the correspondingdownlink of the sTAG on which the preamble is transmitted.

The mapping of a serving cell to a TAG may be configured by a servingeNB with RRC signaling. The mechanism for TAG configuration andreconfiguration may be based on RRC signaling. According to some of thevarious aspects of embodiments, when an eNB performs an SCell additionconfiguration, the related TAG configuration may be configured for theSCell. In an example embodiment, an eNB may modify the TAG configurationof an SCell by removing (releasing) the SCell and adding(configuring) anew SCell (with the same physical cell ID and frequency) with an updatedTAG ID. The new SCell with the updated TAG ID may initially be inactivesubsequent to being assigned the updated TAG ID. The eNB may activatethe updated new SCell and start scheduling packets on the activatedSCell. In an example implementation, it may not be possible to changethe TAG associated with an SCell, but rather, the SCell may need to beremoved and a new SCell may need to be added with another TAG. Forexample, if there is a need to move an SCell from an sTAG to a pTAG, atleast one RRC message, for example, at least one RRC reconfigurationmessage, may be send to the UE to reconfigure TAG configurations byreleasing the SCell and then configuring the SCell as a part of the pTAG(when an SCell is added/configured without a TAG index, the SCell may beexplicitly assigned to the pTAG). The PCell may not change its TA groupand may always be a member of the pTAG.

The purpose of an RRC connection reconfiguration procedure may be tomodify an RRC connection, (e.g. to establish, modify and/or release RBs,to perform handover, to setup, modify, and/or release measurements, toadd, modify, and/or release SCells). If the received RRC ConnectionReconfiguration message includes the sCellToReleaseList, the UE mayperform an SCell release. If the received RRC Connection Reconfigurationmessage includes the sCellToAddModList, the UE may perform SCelladditions or modification.

In LTE Release-10 and Release-11 CA, a PUCCH is only transmitted on thePCell (PSCell) to an eNB. In LTE-Release 12 and earlier, a UE maytransmit PUCCH information on one cell (PCell or PSCell) to a given eNB.

As the number of CA capable UEs and also the number of aggregatedcarriers increase, the number of PUCCHs and also the PUCCH payload sizemay increase. Accommodating the PUCCH transmissions on the PCell maylead to a high PUCCH load on the PCell. A PUCCH on an SCell may beintroduced to offload the PUCCH resource from the PCell. More than onePUCCH may be configured for example, a PUCCH on a PCell and anotherPUCCH on an SCell. FIG. 10 is an example grouping of cells into PUCCHgroups as per an aspect of an embodiment of the present invention. Inthe example embodiments, one, two or more cells may be configured withPUCCH resources for transmitting CSI/ACK/NACK to a base station. Cellsmay be grouped into multiple PUCCH groups, and one or more cell within agroup may be configured with a PUCCH. In an example configuration, oneSCell may belong to one PUCCH group. SCells with a configured PUCCHtransmitted to a base station may be called a PUCCH SCell, and a cellgroup with a common PUCCH resource transmitted to the same base stationmay be called a PUCCH group.

In Release-12, a PUCCH can be configured on a PCell and/or a PSCell, butcannot be configured on other SCells. In an example embodiment, a UE maytransmit a message indicating that the UE supports PUCCH configurationon a PCell and SCell. Such an indication may be separate from anindication of dual connectivity support by the UE. In an exampleembodiment, a UE may support both DC and PUCCH groups. In an exampleembodiment, either DC or PUCCH groups may be configured, but not both.In another example embodiment, more complicated configurationscomprising both DC and PUCCH groups may be supported.

When a UE is capable of configuring PUCCH groups, and if a UE indicatesthat it supports simultaneous PUCCH/PUSCH transmission capability, itmay imply that the UE supports simultaneous PUCCH/PUSCH transmission onboth PCell and SCell. When multiple PUCCH groups are configured, a PUCCHmay be configured or not configured with simultaneous PUCCH/PUSCHtransmission.

In an example embodiment, PUCCH transmission to a base station on twoserving cells may be realized as shown in FIG. 10. A first group ofcells may employ a PUCCH on the PCell and may be called PUCCH group 1 ora primary PUCCH group. A second group of cells may employ a PUCCH on anSCell and may be called PUCCH group 2 or a secondary PUCCH group. One,two or more PUCCH groups may be configured. In an example, cells may begrouped into two PUCCH groups, and each PUCCH group may include a cellwith PUCCH resources. A PCell may provide PUCCH resources for theprimary PUCCH group and an SCell in the secondary PUCCH group mayprovide PUCCH resources for the cells in the secondary PUCCH group. Inan example embodiment, no cross-carrier scheduling between cells indifferent PUCCH groups may be configured. When cross-carrier schedulingbetween cells in different PUCCH groups is not configured, ACK/NACK onPHICH channel may be limited within a PUCCH group. Both downlink anduplink scheduling activity may be separate between cells belonging todifferent PUCCH groups.

A PUCCH on an SCell may carry HARQ-ACK and CSI information. A PCell maybe configured with PUCCH resources. In an example embodiment, RRCparameters for an SCell PUCCH Power Control for a PUCCH on an SCell maybe different from those of a PCell PUCCH. A Transmit Power Controlcommand for a PUCCH on an SCell may be transmitted in DCI(s) on theSCell carrying the PUCCH.

UE procedures on a PUCCH transmission may be different and/orindependent between PUCCH groups. For example, determination of DLHARQ-ACK timing, PUCCH resource determination for HARQ-ACK and/or CSI,Higher-layer configuration of simultaneous HARQ-ACK+CSI on a PUCCH,Higher-layer configuration of simultaneous HARQ-ACK+SRS in one subframemay be configured differently for a PUCCH PCell and a PUCCH SCell.

A PUCCH group may be a group of serving cells configured by a RRC anduse the same serving cell in the group for transmission of a PUCCH. APrimary PUCCH group may be a PUCCH group containing a PCell. A secondaryPUCCH group may be a PUCCH cell group not containing the PCell. In anexample embodiment, an SCell may belong to one PUCCH group. When oneSCell belongs to a PUCCH group, ACK/NACK or CSI for that SCell may betransmitted over the PUCCH in that PUCCH group (over PUCCH SCell orPUCCH PCell). A PUCCH on an SCell may reduce the PUCCH load on thePCell. A PUCCH SCell may be employed for UCI transmission of SCells inthe corresponding PUCCH group.

In an example embodiment, a flexible PUCCH configuration in whichcontrol signaling is sent on one, two or more PUCCHs may be possible.Beside the PCell, it may be possible to configure a selected number ofSCells for PUCCH transmission (herein called PUCCH SCells). Controlsignaling information conveyed in a certain PUCCH SCell may be relatedto a set of SCells in a corresponding PUCCH group that are configured bythe network via RRC signaling.

PUCCH control signaling carried by a PUCCH channel may be distributedbetween a PCell and SCells for off-loading or robustness purposes. Byenabling a PUCCH in an SCell, it may be possible to distribute theoverall CSI reports for a given UE between a PCell and a selected numberof SCells (e.g. PUCCH SCells), thereby limiting PUCCH CSI resourceconsumption by a given UE on a certain cell. It may be possible to mapCSI reports for a certain SCell to a selected PUCCH SCell. An SCell maybe assigned a certain periodicity and time-offset for transmission ofcontrol information. Periodic CSI for a serving cell may be mapped on aPUCCH (on the PCell or on a PUCCH-SCell) via RRC signaling. Thepossibility of distributing CSI reports, HARQ feedbacks, and/orScheduling Requests across PUCCH SCells may provide flexibility andcapacity improvements. HARQ feedback for a serving cell may be mapped ona PUCCH (on the PCell or on a PUCCH SCell) via RRC signaling.

In example embodiments, PUCCH transmission may be configured on a PCell,as well as one SCell in CA. An SCell PUCCH may be realized using theconcept of PUCCH groups, where aggregated cells are grouped into two ormore PUCCH groups. One cell from a PUCCH group may be configured tocarry a PUCCH. More than 5 carriers may be configured. In the exampleembodiments, up to n carriers may be aggregated. For example, n may be16, 32, or 64. Some CCs may have non-backward compatible configurationssupporting only advanced UEs (e.g. support licensed assisted accessSCells). In an example embodiment, one SCell PUCCH (e.g. two PUCCHgroups) may be supported. In another example embodiment, a PUCCH groupconcept with multiple (more than one) SCells carrying PUCCH may beemployed (e.g., there can be more than two PUCCH groups).

In an example embodiment, a given PUCCH group may not comprise servingcells of both MCG and SCG. One of the PUCCHs may be configured on thePCell. In an example embodiment, PUCCH mapping of serving cells may beconfigured by RRC messages. In an example embodiment, a maximum value ofan SCellIndex and a ServCellIndex may be 31 (ranging from 0 to 31). Inan example, a maximum value of stag-Id may be 3. The CIF for a scheduledcell may be configured explicitly. A PUCCH SCell may be configured bygiving a PUCCH configuration for an SCell. A HARQ feedback and CSIreport of a PUCCH SCell may be sent on the PUCCH of that PUCCH SCell.The HARQ feedback and CSI report of a SCell may sent on a PUCCH of aPCell if no PUCCH SCell is signalled for that SCell. The HARQ feedbackand CSI report of an SCell may be sent on the PUCCH of one PUCCH SCell;hence they may not be sent on the PUCCH of different PUCCH SCell. The UEmay report a Type 2 PH for serving cells configured with a PUCCH. In anexample embodiment, a MAC activation/deactivation may be supported for aPUCCH SCell. An eNB may manage the activation/deactivation status forSCells. A newly added PUCCH SCell may be initially deactivated.

In an example embodiment, independent configuration of PUCCH groups andTAGs may be supported. FIG. 11 and FIG. 12 show example configurationsof TAGs and PUCCH groups. For example, one TAG may contain multipleserving cells with a PUCCH. For example, each TAG may only comprisecells of one PUCCH group. For example, a TAG may comprise the servingcells (without a PUCCH) which belong to different PUCCH groups.

There may not be a one-to-one mapping between TAGs and PUCCH groups. Forexample, in a configuration, a PUCCH SCell may belong to primary TAG. Inan example implementation, the serving cells of one PUCCH group may bein different TAGs and serving cells of one TAG may be in different PUCCHgroups. Configuration of PUCCH groups and TAGs may be left to eNBimplementation. In another example implementation, restriction(s) on theconfiguration of a PUCCH cell may be specified. For example, in anexample embodiment, cells in a given PUCCH group may belong to the sameTAG. In an example, an sTAG may only comprise cells of one PUCCH group.In an example, one-to-one mapping between TAGs and PUCCH groups may beimplemented. In implementation, cell configurations may be limited tosome of the examples. In other implementations, some or all the belowconfigurations may be allowed.

In an example embodiment, for an SCell in a pTAG, the timing referencemay be a PCell. For an SCell in an sTAG, the timing reference may be anyactivated SCell in the sTAG. For an SCell (configured with PUCCH or not)in a pTAG, a pathloss reference may be configured to be a PCell or anSIB-2 linked SCell. For an SCell in a sTAG, the pathloss reference maybe the SIB-2 linked SCell. When a TAT associated with a pTAG is expired,the TAT associated with sTAGs may be considered as expired. When a TATof an sTAG containing PUCCH SCell expires, the MAC may indicate to anRRC to release PUCCH resource for the PUCCH group. When the TAT of ansTAG containing a PUCCH SCell is not running, the uplink transmission(PUSCH) for SCells in the secondary PUCCH group not belonging to thesTAG including the PUCCH SCell may not be impacted. The TAT expiry of ansTAG containing a PUCCH SCell may not trigger TAT expiry of other TAGsto which other SCells in the same PUCCH group belong. When the TATassociated with sTAG not containing a PUCCH SCell is not running, thewireless device may stop the uplink transmission for the SCell in thesTAG and may not impact other TAGs.

In an example embodiment, a MAC entity may have a configurable timertimeAlignmentTimer per TAG. The timeAlignmentTimer may be used tocontrol how long the MAC entity considers the Serving Cells belonging tothe associated TAG to be uplink time aligned. The MAC entity may, when aTiming Advance Command MAC control element is received, apply the TimingAdvance Command for the indicated TAG; start or restart thetimeAlignmentTimer associated with the indicated TAG. The MAC entitymay, when a Timing Advance Command is received in a Random AccessResponse message for a serving cell belonging to a TAG and/or if theRandom Access Preamble was not selected by the MAC entity, apply theTiming Advance Command for this TAG and start or restart thetimeAlignmentTimer associated with this TAG. Otherwise, if thetimeAlignmentTimer associated with this TAG is not running, the TimingAdvance Command for this TAG may be applied and the timeAlignmentTimerassociated with this TAG started. When the contention resolution isconsidered not successful, a timeAlignmentTimer associated with this TAGmay be stopped. Otherwise, the MAC entity may ignore the received TimingAdvance Command.

Example embodiments of the invention may enable operation of multiplePUCCH groups. Other example embodiments may comprise a non-transitorytangible computer readable media comprising instructions executable byone or more processors to cause operation of PUCCH groups. Yet otherexample embodiments may comprise an article of manufacture thatcomprises a non-transitory tangible computer readable machine-accessiblemedium having instructions encoded thereon for enabling programmablehardware to cause a device (e.g. wireless communicator, UE, basestation, etc.) to enable operation of PUCCH groups. The device mayinclude processors, memory, interfaces, and/or the like. Other exampleembodiments may comprise communication networks comprising devices suchas base stations, wireless devices (or user equipment: UE), servers,switches, antennas, and/or the like. In an example embodiment one ormore TAGs may be configured along with PUCCH group configuration.

FIG. 13 is an example MAC PDU as per an aspect of an embodiment of thepresent invention. In an example embodiment, a MAC PDU may comprise of aMAC header, zero or more MAC Service Data Units (MAC SDU), zero or moreMAC control elements, and optionally padding. The MAC header and the MACSDUs may be of variable sizes. A MAC PDU header may comprise one or moreMAC PDU subheaders. A subheader may correspond to either a MAC SDU, aMAC control element or padding. A MAC PDU subheader may comprise headerfields R, F2, E, LCID, F, and/or L. The last subheader in the MAC PDUand subheaders for fixed sized MAC control elements may comprise thefour header fields R, F2, E, and/or LCID. A MAC PDU subheadercorresponding to padding may comprise the four header fields R, F2, E,and/or LCID.

In an example embodiment, LCID or Logical Channel ID field may identifythe logical channel instance of the corresponding MAC SDU or the type ofthe corresponding MAC control element or padding. There may be one LCIDfield for a MAC SDU, MAC control element or padding included in the MACPDU. In addition to that, one or two additional LCID fields may beincluded in the MAC PDU when single-byte or two-byte padding is requiredbut cannot be achieved by padding at the end of the MAC PDU. The LCIDfield size may be, e.g. 5 bits. L or the Length field may indicate thelength of the corresponding MAC SDU or variable-sized MAC controlelement in bytes. There may be one L field per MAC PDU subheader exceptfor the last subheader and subheaders corresponding to fixed-sized MACcontrol elements. The size of the L field may be indicated by the Ffield and F2 field. The F or the Format field may indicate the size ofthe Length field. There may be one F field per MAC PDU subheader exceptfor the last subheader and subheaders corresponding to fixed-sized MACcontrol elements and expect for when F2 is set to 1. The size of the Ffield may be 1 bit. In an example, if the F field is included, and/or ifthe size of the MAC SDU or variable-sized MAC control element is lessthan 128 bytes, the value of the F field is set to 0, otherwise it isset to 1. The F2 or the Format2 field may indicate the size of theLength field. There may be one F2 field per MAC PDU subheader. The sizeof the F2 field may be 1 bit. In an example, if the size of the MAC SDUor variable-sized MAC control element is larger than 32767 bytes and ifthe corresponding subheader is not the last subheader, the value of theF2 field may be set to 1, otherwise it is set to 0. The E or theExtension field may be a flag indicating if more fields are present inthe MAC header or not. The E field may be set to “1” to indicate anotherset of at least R/F2/E/LCID fields. The E field may be set to “0” toindicate that either a MAC SDU, a MAC control element or padding startsat the next byte. R or reserved bit, set to “0”.

MAC PDU subheaders may have the same order as the corresponding MACSDUs, MAC control elements and padding. MAC control elements may beplaced before any MAC SDU. Padding may occur at the end of the MAC PDU,except when single-byte or two-byte padding is required. Padding mayhave any value and the MAC entity may ignore it. When padding isperformed at the end of the MAC PDU, zero or more padding bytes may beallowed. When single-byte or two-byte padding is required, one or twoMAC PDU subheaders corresponding to padding may be placed at thebeginning of the MAC PDU before any other MAC PDU subheader. In anexample, a maximum of one MAC PDU may be transmitted per TB per MACentity, a maximum of one MCH MAC PDU can be transmitted per TTI.

At least one RRC message may provide configuration parameters for atleast one cell and configuration parameters for PUCCH groups. Theinformation elements in one or more RRC messages may provide mappingbetween configured cells and PUCCH SCells. Cells may be grouped into aplurality of cell groups and a cell may be assigned to one of theconfigured PUCCH groups. There may be a one-to-one relationship betweenPUCCH groups and cells with configured PUCCH resources. At least one RRCmessage may provide mapping between an SCell and a PUCCH group, andPUCCH configuration on PUCCH SCell.

System information (common parameters) for an SCell may be carried in aRadioResourceConfigCommonSCell in a dedicated RRC message. Some of thePUCCH related information may be included in common information of anSCell (e.g. in the RadioResourceConfigCommonSCell). Dedicatedconfiguration parameters of SCell and PUCCH resources may be configuredby dedicated RRC signaling using, for example,RadioResourceConfigDedicatedSCell.

The IE PUCCH-ConfigCommon and IE PUCCH-ConfigDedicated may be used tospecify the common and the UE specific PUCCH configuration respectively.

In an example, PUCCH-ConfigCommon may include: deltaPUCCH-Shift:ENUMERATED {ds1, ds2, ds3}; nRB-CQI: INTEGER (0 . . . 98); nCS-AN:INTEGER (0 . . . 7); and/or n1PUCCH-AN: INTEGER (0 . . . 2047). Theparameter deltaPUCCH-Shift (Δ_(shift) ^(PUCCH)), nRB-CQI (N_(R) ⁽²⁾,nCS-An (N_(cs) ⁽¹⁾), and n1PUCCH-AN (N_(PUCCH) ⁽¹⁾) may be physicallayer parameters of PUCCH.

PUCCH-ConfigDedicated may be employed. PUCCH-ConfigDedicated mayinclude: ackNackRepetition CHOICE{release: NULL, setup: SEQUENCE{repetitionFactor: ENUMERATED {n2, n4, n6, spare1},n1PUCCH-AN-Rep:INTEGER (0 . . . 2047)}}, tdd-AckNackFeedbackMode: ENUMERATED {bundling,multiplexing} OPTIONAL}. ackNackRepetitionj parameter indicates whetherACK/NACK repetition is configured. n2 corresponds to repetition factor2, n4 to 4 for repetitionFactor parameter (N_(ANRep)). n1PUCCH-AN-Repparameter may be n_(PUCCH,ANRep) ^((1,p)) for antenna port P0 and forantenna port P1. dd-AckNackFeedbackMode parameter may indicate one ofthe TDD ACK/NACK feedback modes used. The value bundling may correspondto use of ACK/NACK bundling whereas, the value multiplexing maycorrespond to ACK/NACK multiplexing. The same value may apply to bothACK/NACK feedback modes on PUCCH as well as on PUSCH.

The parameter PUCCH-ConfigDedicated may include simultaneous PUCCH-PUSCHparameter indicating whether simultaneous PUCCH and PUSCH transmissionsis configured. An E-UTRAN may configure this field for the PCell whenthe nonContiguousUL-RA-WithinCC-Info is set to supported in the band onwhich PCell is configured. The E-UTRAN may configure this field for thePSCell when the nonContiguousUL-RA-WithinCC-Info is set to supported inthe band on which PSCell is configured. The E-UTRAN may configure thisfield for the PUCCH SCell when the nonContiguousUL-RA-WithinCC-Info isset to supported in the band on which PUCCH SCell is configured.

A UE may transmit radio capabilities to an eNB to indicate whether UEsupport the configuration of PUCCH groups. The simultaneous PUCCH-PUSCHin the UE capability message may be applied to both a PCell and anSCell. Simultaneous PUCCH+PUSCH may be configured separately (usingseparate IEs) for a PCell and a PUCCH SCell. For example, a PCell and aPUCCH SCell may have different or the same configurations related tosimultaneous PUCCH+PUSCH.

The eNB may select the PUCCH SCell among current SCells or candidateSCells considering cell loading, carrier quality (e.g. using measurementreports), carrier configuration, and/or other parameters. From afunctionality perspective, a PUCCH Cell group management procedure mayinclude a PUCCH Cell group addition, a PUCCH cell group release, a PUCCHcell group change and/or a PUCCH cell group reconfiguration. The PUCCHcell group addition procedure may be used to add a secondary PUCCH cellgroup (e.g., to add PUCCH SCell and one or more SCells in the secondaryPUCCH cell group). In an example embodiment, cells may be released andadded employing one or more RRC messages. In another example embodiment,cells may be released employing a first RRC message and then addedemploying a second RRC messages.

SCells including PUCCH SCell may be in a deactivated state when they areconfigured. A PUCCH SCell may be activated after an RRC configurationprocedure by an activation MAC CE. An eNB may transmit a MAC CEactivation command to a UE. The UE may activate an SCell in response toreceiving the MAC CE activation command.

In example embodiments, a timer is running once it is started, until itis stopped or until it expires; otherwise it may not be running. A timercan be started if it is not running or restarted if it is running. Forexample, a timer may be started or restarted from its initial value.

Example power headroom trigger condition configuration parameters in anRRC message are shown below. Other examples may be implemented.phr-Config CHOICE {release NULL, setup SEQUENCE {periodicPHR-TimerENUMERATED {sf10, sf20, sf50, sf100, sf200, sf500, sf1000, infinity},prohibitPHR-Timer ENUMERATED {sf0, sf10, sf20, sf50, sf100, sf200,sf500, sf1000}, dl-PathlossChange ENUMERATED {dB1, dB3, dB6, infinity}}

The parameter periodicPHR-Timer may be a timer for PHR reporting. Valuein number of sub-frames. Value sf10 corresponds to 10 subframes, sf20corresponds to 20 subframes and so on.

The parameter prohibitPHR-Timer may be a timer for PHR reporting. Valuein number of sub-frames. Value sf0 corresponds to 0 subframes, sf100corresponds to 100 subframes and so on.

The parameter dl-PathlossChange may be DL Pathloss Change and the changeof the required power backoff due to power management (as allowed byP-MPRc) for PHR reporting. Value in dB. Value dB1 corresponds to 1 dB,dB3 corresponds to 3 dB and so on. The same value may apply for eachserving cell (although the associated functionality is performedindependently for each cell).

A Power Headroom reporting procedure may be employed to provide aserving eNB with information about the difference between nominal UEmaximum transmit power and estimated power for UL-SCH transmission peractivated serving cell. The Power Headroom reporting procedure may alsoto provide a serving eNB with information about the difference betweenthe nominal UE maximum power and the estimated power for an UL-SCH andPUCCH transmission on a SpCell and/or a PUCCH SCell.

The reporting period, delay and mapping of Power Headroom may bedefined. An RRC may control Power Headroom reporting by configuring atleast two timers periodicPHR-Timer and prohibitPHR-Timer, and bysignalling dl-PathlossChange which may set the change in measureddownlink pathloss and the power backoff due to power management (asallowed by P-MPR_(c)) to trigger a PHR.

In an example embodiment, a Power Headroom Report (PHR) may be triggeredif one or more of the following events occur (not listed in anyparticular order). First, a prohibitPHR-Timer expires or has expired andthe path loss has changed more than dl-PathlossChange dB for at leastone activated serving cell of any MAC entity which is used as a pathlossreference since the last transmission of a PHR in this MAC entity whenthe MAC entity has UL resources for new transmission. Second, aperiodicPHR-Timer expires. Third, upon configuration or reconfigurationof the power headroom reporting functionality by upper layers, which isnot used to disable the function. Fourth, activation of an SCell of anyMAC entity with a configured uplink; Fifth, addition of an PSCell;and/or sixth, a prohibitPHR-Timer expires or has expired, when the MACentity has UL resources for a new transmission, and the following istrue in this TTI for any of the activated serving cells of any MACentity with a configured uplink (there may be UL resources allocated fortransmission or there may be a PUCCH transmission on this cell, and therequired power backoff due to power management (as allowed by P-MPRc)for this cell has changed more than dl-PathlossChange dB since the lasttransmission of a PHR when the MAC entity had UL resources allocated fortransmission or PUCCH transmission on this cell).

In an example implementation, the MAC entity may avoid triggering a PHRwhen the required power backoff due to power management decreasestemporarily (e.g. for up to a few tens of milliseconds) and it may avoidreflecting such temporary decrease in the values of PCMAX,c/PH when aPHR is triggered by other triggering conditions.

If the MAC entity has UL resources allocated for a new transmission forthis TTI, the MAC entity may start a periodicPHR-Timer if it is thefirst UL resource allocated for a new transmission since the last MACreset. A UE may transmit a corresponding PHR report if a Power Headroomreporting procedure determines that at least one PHR has been triggeredand not cancelled, and if the allocated UL resources can accommodate acorresponding PHR MAC control element plus its subheader for acorresponding PHR configuration as a result of logical channelprioritization.

For example, a UE may transmit a corresponding PHR report for one ormore activated serving cells with a configured uplink if: the allocatedUL resources can accommodate a PHR MAC control element plus itssubheader if neither extendedPHR nor dualConnectivityPHR is configured,and/or an Extended PHR MAC control element plus its subheader if anextendedPHR is configured, and/or a Dual Connectivity PHR MAC controlelement plus its subheader if dualConnectivityPHR is configured as aresult of logical channel prioritization.

In LTE Release-10 carrier aggregation (CA), an Extended Power HeadroomReport (PHR) MAC Control Element (CE) was introduced to accommodate type2 power headroom (PH) of PCell and type 1 PHs of SCells. Type 2 PH maybe employed when simultaneous PUCCH-PUSCH configuration is supported. InDC, since a PUCCH may be transmitted on a PCell and an PSCell, the PHRMAC CE may contain 2 type 2 PHs and several type 1 PHs. DC PHR MAC CEwas introduced to include an extra type 2 PH of a PSCell. For DC, PH maybe reported to both eNB s separately, but the PHR may include PH foractive serving cells.

In LTE Release-12, three types of power headroom related MAC CEs aredefined: 1) a Power Headroom Report MAC CE, 2) An Extended PowerHeadroom Report MAC CE, and 3) Dual Connectivity Power Headroom. A MACCE may be identified by a logical channel ID (LCID) field in a MACsubheader. The LCID field may identify the logical channel instance ofthe corresponding MAC SDU and/or the type of the corresponding MACcontrol element and/or padding.

Values of LCID for UL-SCH MAC CE in Release-12 are defined in 3GPP TS36.321 V12.4.0 as: Index 11000: Dual Connectivity Power Headroom Report;Index 11001: Extended Power Headroom Report; and Index 11010: PowerHeadroom Report

If an extendedPHR mode is configured and when conditions fortransmission of a PHR are met, a UE may generate and transmit anExtended PHR MAC control element identified by, for example, LCID=11001.

If a dualConnectivityPHR mode is configured and when conditions fortransmission of a PHR are met, a UE may generate and transmit a DualConnectivity Power Headroom Report identified by, for example,LCID=11000.

If a PHR is configured but neither extendedPHR mode nordualConnectivityPHR mode is configured, and when conditions fortransmission of a PHR are met, then a UE may generate and transmit aPower Headroom Report with, for example, an LCID of 11010.

LTE Release-12 does not appear to address configuration, message format,trigger conditions, and message processing for power headroom when aPUCCH SCell with simultaneous PUCCH+PUSCH transmissions is configured ina UE (without configuring DC in the UE). A Release-12 Dual ConnectivityPower Headroom Report may not be applicable in such a scenario, sincedual connectivity may not be configured in the UE. A Release-12 ExtendedPower Headroom Report may not be applicable since it does not appear tosupport transmission of two Type 2 power headrooms when PUCCH groups areconfigured. A Release-12 Power Headroom Report report may not beapplicable since it appears to support only one serving cell. There maybe a need for enhancing the power headroom implementation to efficientlysupport PUCCH group configuration. There may also be a need forenhancing the power headroom implementation to enhanced cellconfigurations not supported by existing PHR formats.

A new PHR may be called an extendedPHR2 MAC CE and/or an extended cellconfiguration PHR MAC CE and/or a new extended PHR MAC CE. The new PHRmay also be called by other names (e.g. PUCCH group PHR MAC CE, enhancedconfiguration MAC CE, 32 cell PHR MAC CE, etc., and/or the like). AnExtendedPHR2 MAC CE may also support additional features in addition toPUCCH groups. For example, an ExtendedPHR2 MAC CE may support more than5 cells including a primary cell and more than k secondary cells (e.g.k=4, 7, etc, may support up to 32 cells) and/or many other features.

The number of used MAC LCIDs may increase if a new PHR MAC CE commandformat with a new MAC LCID is implemented for an extendedPHR2. A MACLCID may be included in a MAC subheader. In an example embodiment, anexisting MAC LCID may be employed for an extendedPHR2 (e.g. LCID ofExtended PHR). A UE may transmit PHR MAC CEs to an eNB in unicastmessages. Both the UE and the eNB may have information about the currentRRC configurations of the UE. The UE may use the same LCID for or one ormore PHR transmissions and the UE may identify the format of the PHRbased on RRC configuration parameters.

This enhancement may not require introducing a new LCID for anextendedPHR2. Two different power headroom MAC CEs may use the sameLCID. This mechanism may reduce the number of LCIDs used in the MAClayer (compared with the scenario wherein a new LCID is introduced) andmay further simplify a UE implementation. RRC configuration parametersin addition to an LCID may be employed to determine the format of thePHR MAC CE.

A UE may consider UE RRC cell configurations to decide the format of aPHR MAC CE. For example, if a UE is configured with a first RRCconfiguration for a plurality of cells (e.g. 5 cells) of an eNB with noconfigured PUCCH SCell, then the fields in the MAC CE may be updatedusing processes related to an extendedPHR power headroom. If a UE isconfigured with PUCCH groups, then the fields in the MAC CE may beupdated using processes related to an extendedPHR2 PHR. On the otherhand, an eNB receiving the PHR MAC CE may have information about the RRCconfiguration of the UE transmitting the PHR MAC CE, and may interpretthe PHR MAC CE fields based on the corresponding RRC configuration.

An eNB may transmit one or more RRC configuration parameters comprisingconfiguration parameters of one or more cells. The configurationparameters for a cell may comprise configuration parameters for powerheadroom. The UE may use RRC configuration parameters to determine whichtype of the PHR headroom the UE should transmit.

In an example embodiment, a UE may transmit its capability regardingsupporting simultaneousPUCCH-PUSCH to the eNB in an RRC UE CapabilityIE. For example: simultaneousPUCCH-PUSCH-r10 ENUMERATED {supported}OPTIONAL. The eNB may then configure simultaneousPUCCH-PUSCH for PCelland/or PUCCH SCell using information elements in RRC control messages.For example: simultaneousPUCCH-PUSCH ENUMERATED {true} OPTIONAL, NeedOR. simultaneousPUCCH-PUSCH IE may indicate whether simultaneous PUCCHand PUSCH transmissions is configured in a PUCCH group. In an example,E-UTRAN may configure this field, when thenonContiguousUL-RA-WithinCC-Info is set to supported in the band onwhich PCell (or e.g. PUCCH SCell) is configured.

In LTE-A release 12 and before, Type 2 power headroom is reported whensimultaneousPUCCH-PUSCH is configured for a given cell, for examplePCell or PSCell. PCell and PSCell are always active after they areconfigured. When simultaneousPUCCH-PUSCH is configured, Type 1 and Type2 PH fields for PCell and PSCell are included in the PHR report.simultaneousPUCCH-PUSCH may be configured for PUCCH SCell. In Release 12and before, the presence of Type2 PH depends on thesimultaneousPUCCH-PUSCH configuration. If a UE is not configured withsimultaneousPUCCH-PUSCH, the UE transmits UCI on PUSCH and the paralleltransmission of PUCCH and PUSCH does not occur. In this case, the UEdoes not transmit Type2 PH in the PHR report. When a UE is configuredwith simultaneousPUCCH-PUSCH, the UE may transmit UCI on PUCCH whenPUSCH resource is allocated. In this case, the UE transmits Type2 PH inthe PHR report.

In 3GPP RAN2 meeting number 91 in September 2015, it was agreed thatpresence of Type 2 PH for both PCell and PUCCH SCell follows theconfiguration of simultaneousPUCCH-PUSCH of the corresponding PUCCH. IfsimultaneousPUCCH-PUSCH is not configured for a PUCCH group, then Type 2PH is not reported for that group. This mechanism may createinefficiencies and/or issues when multiple PUCCH groups are configured.This mechanism may not provide adequate transmit power information tothe eNB for an efficient uplink scheduling and power control. Whenmultiple PUCCH groups are configured and when simultaneousPUCCH-PUSCH isnot configured for a cell group, parallel transmission of PUSCH and UCImay still be possible. In an example embodiment, UCI in one PUCCH groupmay be transmitted in parallel with PUSCH in another PUCCH group. Thereis a need to improve mechanisms for transmission of Type 2 PHR for thePCell and PUCCH SCell based on RRC configuration parameters when PUCCHgroups are configured.

When PUCCH groups are configured, UCI multiplexing on PUSCH is on perPUCCH group basis. The simultaneous transmission of PUCCH and PUSCH mayoccur when UE is configured with PUCCH SCell and simultaneousPUCCH-PUSCHis not configured.

In an example embodiment, when PUCCH groups are configured, UCI on PUSCHis performed per PUCCH group. A UE may multiplex UCIs of a primary PUCCHgroup on the PUSCH of a serving cell in primary PUCCH group. A UE maynot multiplex UCIs of primary PUCCH group on PUSCH of a serving cell insecondary PUCCH group. A UE may multiplex UCIs of a secondary PUCCHgroup on the PUSCH of a serving cell in the secondary PUCCH group. A UEmay not multiplex UCIs of a secondary PUCCH group on PUSCH of a servingcell in another PUCCH group, e.g. the primary PUCCH group.

When PUCCH groups are configured, the configuration ofsimultaneousPUCCH-PUSCH may be configured independently on PCell orPUCCH SCell. For example, the parameter simultaneousPUCCH-PUSCH may beconfigured on both PCell and PUCCH SCell (set as true). For example,simultaneousPUCCH-PUSCH may be configured for one of PCell or PUCCHSCell. Or in another example, simultaneousPUCCH-PUSCH may not beconfigured on either PCell or PUCCH SCell.

In an example embodiment, independent of whether simultaneousPUCCH-PUSCHis configured (set to true) or not, UCI in one cell group may betransmitted in PUCCH of one cell group, in parallel with PUSCHtransmission in another cell group. Even when simultaneousPUCCH-PUSCH isconfigured for neither PCell nor PUCCH SCell, parallel transmission ofPUCCH and PUSCH is still possible. If UE is configured with PUCCH SCell,simultaneous transmission of PUCCH and PUSCH may occur independent ofthe configuration of simultaneousPUCCH-PUSCH on either PCell or PUCCHSCell.

According to the current agreement, a PHR may be reported without anyType 2 PH even if PUCCH can be transmitted in the same subframe asPUSCH. Such PHR transmission mechanism may not provide adequate powerheadroom information to eNB for an efficient uplink power control. Inrelease 13 carrier aggregation, PUCCH groups may be configured under oneMAC entity. A UE may transmit multiple PUCCHs to the same eNB.

In an example solution to this problem, a mechanism may be implementedin which Type 2 PH is reported for PCell when PUCCH on SCell isconfigured, regardless of configuration of simultaneousPUCCH-PUSCH oneither PCell or PUCCH SCell. Such mechanism may result in additionalinefficiencies. The mechanism may transmit Type 2 PHR for a PCell whenit is not needed by the eNB. A PUCCH SCell may be deactivated and inthat case the above mechanism may transmit unnecessary PCell Type 2power headroom (e.g. even if simultaneousPUCCH-PUSCH is not configuredfor the PCell). Such solution may provide unneeded PCell Type 2 PHR tothe eNB in some scenarios.

In an example solution, Type 2 PH may be reported for PUCCH SCell whenPUCCH on SCell is configured, regardless of configuration ofsimultaneousPUCCH-PUSCH on either PCell or PUCCH SCell. Such mechanismmay transmit Type 2 PHR for an SCell when it is not needed by the eNB,for example when PUCCH SCell is deactivated. This mechanism may resultin additional signaling overhead and computation on the UE. A moreeffective mechanism may be needed to enhance PHR report process andmechanism in a UE and an eNB.

Examples in the above two paragraphs are examples of inefficientsolutions. There is a need to further improve PHR process. An exampleembodiment, enhance PHR transmission mechanisms, e.g, when multiplePUCCH SCells are configured.

In an example embodiment, Type 1 and Type 2 PH may not be transmittedfor a deactivated PUCCH SCell when PUCCH on SCell is configured. Type 2PH is transmitted for an activated PUCCH SCell regardless of whethersimultaneousPUCCH-PUSCH is configured for the PUCCH SCell or not.

In an example embodiment, a PUCCH SCell may be deactivated in somescenarios. If and when PUCCH SCell is deactivated, there is no need toinclude Type 1 and Type 2 PH reports in the PHR for the PUCCH SCell.This requires implementation of new processes and format of PHR, inwhich Type 2 and/or Type 1 PHR may or may not be reported for a PUCCHSCell.

In an example embodiment, a PUCCH SCell may be deactivated in somescenarios. Transmission of Type 2 PH for a PCell may depend on whetherPUCCH SCell is activated or deactivated. When a PUCCH SCell isconfigured and activated, Type 2 PH is transmitted for the PCell and thePUCCH SCell regardless of whether simultaneousPUCCH-PUSCH is configuredor not configured for the PCell and/or the PUCCH SCell. When the PUCCHSCell is activated, UCI on PUCCH may be transmitted in parallel withPUSCH regardless of whether simultaneousPUCCH-PUSCH is configured forthe PCell or not.

When a PUCCH SCell is configured and deactivated, a Type 2 PH istransmitted for the PCell only when simultaneousPUCCH-PUSCH isconfigured for the PCell. When PUCCH SCell is deactivated, UCI on PUCCHof PCell may not be transmitted in parallel with PUSCH whensimultaneousPUCCH-PUSCH is not configured. When PUCCH SCell isdeactivated, UCI on PUCCH may be transmitted in parallel with PUSCH whensimultaneousPUCCH-PUSCH is configured.

In an example embodiment, when extendedPHR2 PHR is reported, themechanism for reporting Type 2 PH may be according to the followingprocess:

if a PUCCH SCell is configured and activated: (regardless ofconfiguration of simultaneousPUCCH-PUSCH)

-   -   obtain the value of the Type 2 power headroom for the PCell;    -   obtain the value for the corresponding P_(CMAX,c) field from the        physical layer;    -   obtain the value of the Type 2 power headroom for the PUCCH        SCell    -   obtain the value for the corresponding P_(CMAX,c) field from the        physical layer;        else if simultaneousPUCCH-PUSCH is configured for PCell:    -   obtain the value of the Type 2 power headroom for the PCell;    -   obtain the value for the corresponding P_(CMAX,c) field from the        physical layer.

In above example, Type 2 PHR is not reported whensimultaneousPUCCH-PUSCH for PCell is not configured, and PUCCH SCell isconfigured and deactivated.

An example procedure for reporting extended power headroom is shownbelow:

In an example embodiment, if the MAC entity has UL resources allocatedfor new transmission for this TTI the MAC entity may: if it is the firstUL resource allocated for a new transmission since the last MAC reset,start periodicPHR-Timer; if the Power Headroom reporting proceduredetermines that at least one PHR has been triggered and not cancelled,and; if the allocated UL resources can accommodate a PHR MAC controlelement plus its subheader if neither extendedPHR nordualConnectivityPHR is configured, or the Extended PHR MAC controlelement plus its subheader if extendedPHR is configured, or the DualConnectivity PHR MAC control element plus its subheader ifdualConnectivityPHR is configured, as a result of logical channelprioritization:

-   -   if extendedPHR is configured:        -   for each activated Serving Cell with configured uplink:            -   obtain the value of the Type 1 power headroom;            -   if the MAC entity has UL resources allocated for                transmission on this Serving Cell for this TTI:                -   obtain the value for the corresponding P_(CMAX,c)                    field from the physical layer;        -   if simultaneousPUCCH-PUSCH is configured:            -   obtain the value of the Type 2 power headroom for the                PCell;            -   if the MAC entity has a PUCCH transmission in this TTI:                -   obtain the value for the corresponding P_(CMAX,c)                    field from the physical layer;        -   instruct the Multiplexing and Assembly procedure to generate            and transmit an Extended PHR MAC control element for            extendedPHR based on the values reported by the physical            layer;    -   else if extendedPHR2 is configured:        -   for each activated Serving Cell with configured uplink:            -   obtain the value of the Type 1 power headroom;            -   if the MAC entity has UL resources allocated for                transmission on this Serving Cell for this TTI:                -   obtain the value for the corresponding P_(CMAX,c)                    field from the physical layer;        -   if PUCCH SCell is configured and activated:            -   obtain the value of the Type 2 power headroom for the                PCell;            -   obtain the value for the corresponding P_(CMAX,c) field                from the physical layer;            -   obtain the value of the Type 2 power headroom for the                PUCCH SCell            -   obtain the value for the corresponding P_(CMAX,c) field                from the physical layer;        -   else if simultaneousPUCCH-PUSCH is configured for PCell:            -   obtain the value of the Type 2 power headroom for the                PCell;            -   obtain the value for the corresponding P_(CMAX,c) field                from the physical layer;

The MAC layer in the UE may instruct the Multiplexing and Assemblyprocedure to generate and transmit an Extended PHR MAC control elementfor extendedPHR2 according to configured ServCellIndex and the PUCCH(s)for the MAC entity based on the values reported by the physical layer.

Activation/Deactivation may be supported for PUCCH SCell. While thePUCCH SCell is deactivated in a PUCCH group, SCells belonging to thePUCCH group may not be activated. The eNB is supposed to manage theactivation/deactivation status. The eNB is supposed to deactivate anSCell when its PUCCH is remapped to a deactivated PUCCH SCell.

There may be two types of UE power headroom reports, Type 1 and Type 2.A UE power headroom PH may be valid for subframe i for serving cell c.

If the UE is configured with an SCG, and if a higher layer parameterphr-ModeOtherCG-r12 for a CG indicates ‘virtual’ for power headroomreports transmitted on that CG, the UE may compute PH assuming that itdoes not transmit a PUSCH/PUCCH on any serving cell of the other CG.

If the UE is configured with an SCG for computing power headroom forcells belonging to MCG, the term ‘serving cell’ may refer to a servingcell belonging to the MCG. For computing power headroom for cellsbelonging to an SCG, the term ‘serving cell’ may refer to a serving cellbelonging to the SCG. The term ‘primary cell’ may refer to the PSCell ofthe SCG. If the UE is configured with a PUCCH SCell for computing powerheadroom for cells belonging to a primary PUCCH group, the term ‘servingcell’ may refer to a serving cell belonging to the primary PUCCH group.For computing power headroom for cells belonging to a secondary PUCCHgroup, the term ‘serving cell’ may refer to serving cell belonging tothe secondary PUCCH group. The term ‘primary cell’ may refer to thePUCCH-SCell of the secondary PUCCH group.

An example Type 1 and Type 2 power headroom calculations is presentedhere. Example parameters and example calculation method is presented instandard document 3GPP TS 36.213 standard documents of the correspondingLTE release.

Type 1:

If the UE transmits PUSCH without PUCCH in subframe i for serving cellc, power headroom for a Type 1 report may be computed usingPH _(type1,c)(i)=P _(CMAX,c)−{10 log₁₀(M _(PUSCH,c)(i))+P_(O_PUSCH,c)(j)+α_(c)(j)·PL _(c)+Δ_(TF,c)(i)+f _(c)(i)} [dB]where, example P_(CMAX,c)(i), M_(PUSCH,c)(i) P_(O_PUSCH,c)(j) α_(c)(j),PL_(c), Δ_(TF,c)(i) and f_(c)(i) may be defined as follows.P_(CMAX,c)(i) may be the configured UE transmit power in subframe i forserving cell c and {circumflex over (P)}_(CMAX,c)(i) may be the linearvalue of P_(CMAX,c)(i). M_(PUSCH,c)(i) may be the bandwidth of the PUSCHresource assignment expressed in number of resource blocks valid forsubframe i and serving cell c. Po_PUSCH, c(j) may be configuredemploying RRC configuration parameters. If the UE is configured withhigher layer parameter UplinkPowerControlDedicated-v12x0 for servingcell c and if subframe i belongs to uplink power control subframe set 2as indicated by the higher layer parameter tpc-SubframeSet-r12. For j=0or 1, α_(c)(j)=α_(c,2)∈{0, 0.4, 0.5, 0.6, 0.7, 0.8, 0.9, 1}. α_(c,2) isthe parameter alpha-SubframeSet2-r12 provided by higher layers for eachserving cell c. For j=2, α_(c)(j)=1. Otherwise: For j=0 or 1, α_(c)∈{0,0.4, 0.5, 0.6, 0.7, 0.8, 0.9, 1} may be a 3-bit parameter provided byhigher layers for serving cell c. For j=2, α_(c)(j)=1; PL_(c) may be thedownlink path loss estimate calculated in the UE for serving cell c indB and PL_(c)=referenceSignalPower−higher layer filtered RSRP, wherereferenceSignalPower is provided by higher layers and RSRP for thereference serving cell and the higher layer filter configuration for thereference serving cell; Δ_(TF,c)(i)=10 log₁₀((2^(BPRE·K) ^(s)−1)·β_(offset) ^(PUSCH)) for K_(S)=1.25 and 0 for K_(S)=0 where K_(S) isgiven by the parameter deltaMCS-Enabled provided by higher layers foreach serving cell c. BPRE and β_(offset) ^(PUSCH), for each serving cellc, are computed as below. K_(S)=0 for transmission mode 2; f(i) may be afunction of power control commands.

PL_(c) is, for example, the downlink path loss estimate calculated inthe UE for serving cell c in dB and PL_(c)=referenceSignalPower—higherlayer filtered RSRP, where referenceSignalPower is provided by higherlayers. The UE may measure on or more pathloss values employing signalsreceived on one or more pathloss reference cells. A pathloss referencecell may be configured for a serving cell. The UE may calculate PL_(c)and may employ one or more pathloss values (PL_(c)) for calculation ofType 1 and Type 2 power headroom fields. If serving cell c belongs to aTAG containing the primary cell then, for the uplink of the primarycell, the primary cell may be used as the reference serving cell fordetermining referenceSignalPower and higher layer filtered RSRP. For theuplink of the secondary cell, the serving cell configured by the higherlayer parameter pathlossReferenceLinking may be used as the referenceserving cell for determining referenceSignalPower and higher layerfiltered RSRP. If serving cell c belongs to a TAG containing the PSCellthen, for the uplink of the PSCell, the PSCell may be used as thereference serving cell for determining referenceSignalPower and higherlayer filtered RSRP. For the uplink of the secondary cell other thanPSCell, the serving cell configured by the higher layer parameterpathlossReferenceLinking may be used as the reference serving cell fordetermining referenceSignalPower and higher layer filtered RSRP.

If the UE transmits PUSCH with PUCCH in subframe/for serving cell c,power headroom for a Type 1 report may be computed using:PH _(type1,c)(i)={tilde over (P)} _(CMAX,c)(i)−{10 log₁₀(M_(PUSCH,c)(i))+P _(O_PUSCH,c)(j)+α_(c)(j)·PL _(c)+Δ_(TF,c)(i)+f _(c)(i)}[dB]{tilde over (P)}_(CMAX,c)(i) may be computed assuming a PUSCH onlytransmission in subframe i. For this case, the physical layer maydeliver {tilde over (P)}_(CMAX,c) (i) instead of P_(CMAX,c) (i) tohigher layers. If the UE does not transmit PUSCH in subframe i forserving cell c, power headroom for a Type 1 report may be computed usingPH _(type1,c)(i)={tilde over (P)} _(CMAX,c)(i)−{P_(O_PUSCH,c)(1)+α_(c)(1)·PL _(c) +f _(c)(i)} [dB]where, example P_(CMAX,c)(i) may be computed assuming MPR=0 dB, A-MPR=0dB, P-MPR=0 dB and ⋅TC=0 dB.

Type 2:

If the UE transmits PUSCH simultaneous with PUCCH in subframe/for theprimary cell, power headroom for a Type 2 report is computed using:

$\begin{matrix}{{P{H_{{type}\; 2}(i)}} = {{P_{{CMAX},c}(i)} - {10\log_{10}{\quad{\left( \begin{matrix}10^{{({{\log_{10}{({M_{{PUSCH},c}{(i)}})}} + {P_{{O\_ PUSCH},c}{(j)}} + {{\alpha_{c}{(j)}} \cdot {PL}_{c}} + {\Delta_{{TF},c}{(i)}} + {f_{c}{(i)}}})}\text{/}10} \\{+ 10^{{({P_{0{\_{PUCCH}}} + {PL}_{c} + {h{({n_{CQI},n_{HARQ},n_{SR}})}} + {\Delta_{F\_ PUCCH}{(F)}} + {\Delta_{TxD}{(F^{\prime})}} + {g{(i)}}})}\text{/}10}}\end{matrix} \right)\lbrack{dB}\rbrack}}}}} & \;\end{matrix}$If the UE transmits PUSCH without PUCCH in subframe i for the primarycell, power headroom for a Type 2 report is computed using:

${P{H_{{type}\; 2}(i)}} = {{P_{{CMAX},c}(i)} - {10\log_{10}{\quad{\begin{pmatrix}10^{{({{\log_{10}{({M_{{PUSCH},c}{(i)}})}} + {P_{{O\_ PUSCH},c}{(j)}} + {{\alpha_{c}{(j)}} \cdot {PL}_{c}} + {\Delta_{{TF},c}{(i)}} + {f_{c}{(i)}}})}\text{/}10} \\{+ 10^{{({P_{0{\_{PUCCH}}} + {PL}_{c} + {g{(i)}}})}\text{/}10}}\end{pmatrix}\lbrack{dB}\rbrack}}}}$where, example P_(CMAX,c)(i), M_(PUSCH,c)(i) P_(O_PUSCH,c)(j), α_(c)(j),Δ_(TF,c)(i) and f_(c)(i) may be of the primary cell parameters. If theUE transmits PUCCH without PUSCH in subframe i for the primary cell,power headroom for a Type 2 report is computed using:

${P{H_{{type}\; 2}(i)}} = {{P_{{CMAX},c}(i)} - {10\log_{10}{\quad{\left( \begin{matrix}10^{{({{P_{{O\_ PUSCH},c}{(1)}} + {{\alpha_{c}{(1)}} \cdot {PL}_{c}} + {f_{c}{(i)}}})}\text{/}10} \\{+ 10^{{({P_{0{\_{PUCCH}}} + {PL}_{c} + {h{({n_{CQI},n_{HARQ},n_{SR}})}} + {\Delta_{F\_ PUCCH}{(F)}} + {\Delta_{TxD}{(F^{\prime})}} + {g{(i)}}})}\text{/}10}}\end{matrix} \right)\lbrack{dB}\rbrack}}}}$where, example P_(O_PUSCH,c)(1), α_(c)(1) and f_(c)(i) are the primarycell parameters. If the UE does not transmit PUCCH or PUSCH in subframei for the primary cell, power headroom for a Type 2 report is computedusing:

$\begin{matrix}{{P{H_{{type}\; 2}(i)}} = {{{\overset{\sim}{P}}_{{CMAX},c}(i)} - {10{{\log_{10}\begin{pmatrix}10^{{({{P_{{O\_ PUSCH},c}{(1)}} + {{\alpha_{c}{(1)}} \cdot {PL}_{c}} + {f_{c}{(i)}}})}\text{/}10} \\{+ 10^{{({P_{0{\_{PUCCH}}} + {PL}_{c} + {g{(i)}}})}\text{/}10}}\end{pmatrix}}\lbrack{dB}\rbrack}}}} & \;\end{matrix}$where, example {tilde over (P)}_(CMAX,c)(i) may be computed assumingMPR=0 dB, A-MPR=0 dB, P-MPR=0 dB and Tc=0 dB, P_(O_PUSCH,c)(1), α_(c)(1)and f_(c)(i) are the primary cell parameters. If the UE is unable todetermine whether there is a PUCCH transmission corresponding to PDSCHtransmission(s) or not, or which PUCCH resource is used, in subframe ifor the primary cell, before generating power headroom for a Type 2report, upon (E)PDCCH detection, with the following conditions: (1) ifboth PUCCH format 1b with channel selection and simultaneousPUCCH-PUSCHare configured for the UE, or (2) if PUCCH format 1b with channelselection is used for HARQ-ACK feedback for the UE configured with PUCCHformat 3 and simultaneousPUCCH-PUSCH are configured, then, UE may beallowed to compute power headroom for a Type 2 using:

${P{H_{{type}\; 2}(i)}} = {{P_{{CMAX},c}(i)} - {10\log_{10}{\quad{\begin{pmatrix}10^{{({{\log_{10}{({M_{{PUSCH},c}{(i)}})}} + {P_{{O\_ PUSCH},c}{(j)}} + {{\alpha_{c}{(j)}} \cdot {PL}_{c}} + {\Delta_{{TF},c}{(i)}} + {f_{c}{(i)}}})}\text{/}10} \\{+ 10^{{({P_{0{\_{PUCCH}}} + {PL}_{c} + {g{(i)}}})}\text{/}10}}\end{pmatrix}\lbrack{dB}\rbrack}}}}$where, example P_(CMAX,c)(i), M_(PUSCH,c)(i) P_(O_PUSCH,c)(j), α_(c)(j),Δ_(TF,c)(i) and f_(c)(i) are the primary cell parameters.

The power headroom may be rounded to the closest value in the range [40;−23] dB with steps of 1 dB and is delivered by the physical layer tohigher layers. If the UE is configured with higher layer parameterUplinkPowerControlDedicated-v12x0 for serving cell c and ifsubframe/belongs to uplink power control subframe set 2 as indicated bythe higher layer parameter tpc-SubframeSet-r12, the UE may usef_(c,2)(i) instead of f_(c)(i) to compute PH_(type1,c)(i) andPH_(type2,c)(i) for subframe i and serving cell c.

FIG. 14 is an example flow diagram as per an aspect of an embodiment ofthe present invention. According to an embodiment, a wireless device maycomprise one or more processors and memory storing instructions that,when executed, cause the wireless device to perform at least part of theflow diagram. A wireless device may receive at least one message from abase station at 1410. The at least one message may comprise a firstparameter and a second parameter. The first parameter may indicatewhether simultaneous physical uplink control channel (PUCCH) andphysical uplink shared channel (PUSCH) transmission is configured forthe primary cell. The second parameter may indicate whether simultaneousPUCCH and PUSCH transmission is configured for the PUCCH secondary cell(SCell).

The at least one message may comprise configuration parameters of aplurality of cells. The plurality of cells may be grouped into aplurality of PUCCH groups. The plurality of PUCCH groups may comprise aprimary PUCCH group a secondary PUCCH group. The primary PUCCH group maycomprise the primary cell. The secondary PUCCH group may comprise thePUCCH SCell.

The wireless device may further calculate a Type 2 power headroom levelemploying: a PUCCH calculated power; and/or a PUSCH calculated power. AType 1 power headroom level may be calculated employing the PUSCHcalculated power.

A power headroom (PH) report comprising a first Type 2 PH field for theprimary cell and a second Type 2 PH field for the PUCCH SCell (1440) maybe transmitted at 1460 if the PUCCH SCell is activated (1420) (This maybe regardless of whether simultaneous PUCCH and PUSCH transmission isconfigured for the primary cell or the PUCCH SCell.). Otherwise, a powerheadroom (PH) report comprising the first Type 2 PH field for theprimary cell and no PH field for the PUCCH SCell (1450) may betransmitted at 1460 if simultaneous PUCCH and PUSCH transmission isconfigured for the primary cell (1430). If PUCCH SCell is deactivatedand simultaneous PUCCH and PUSCH transmission is not configured for theprimary cell, the UE (wireless device) may transmit a power headroomthat does not comprise any Type 2 power headroom.

The wireless device may further measure one or more pathloss valuesemploying signals received on one or more pathloss reference cells. Oneor more fields of the PH report may be calculated employing the one ormore pathloss values. A media access control (MAC) control element (CE)comprising the PH report may be identified by a subheader. The subheadermay comprise a logical channel identifier (LCID) field and/or a lengthfield. The PH report may comprises one or more Type 1 power headroomfields. The PH report may be configured to be employed by a base stationfor at least one of uplink packet scheduling or uplink power control.

FIG. 15 is an example flow diagram as per an aspect of an embodiment ofthe present invention. According to an embodiment, a base station maycomprise one or more processors and memory storing instructions that,when executed, cause the base station to perform at least part of theflow diagram. A base station may transmit at least one message to awireless device at 1510. The at least one message may comprise a firstparameter and a second parameter. The first parameter may indicatewhether simultaneous physical uplink control channel (PUCCH) andphysical uplink shared channel (PUSCH) transmission is configured for aprimary cell. The second parameter may indicate whether simultaneousPUCCH and PUSCH transmission is configured for a PUCCH secondary cell(SCell).

The at least one message may comprise configuration parameters of aplurality of cells. The plurality of cells may be grouped into aplurality of PUCCH groups. The plurality of PUCCH groups may comprise aprimary PUCCH group a secondary PUCCH group. The primary PUCCH group maycomprise the primary cell. The secondary PUCCH group may comprise thePUCCH SCell.

If the PUCCH SCell is activated (1520), the wireless device may receivea power headroom (PH) report at 1540 that comprises a first Type 2 PHfield for the primary cell and a second Type 2 PH field for the PUCCHSCell. This may be regardless of whether simultaneous PUCCH and PUSCHtransmission is configured for the primary cell or the PUCCH SCell.Otherwise, if simultaneous PUCCH and PUSCH transmission is configuredfor the primary cell (1530), the wireless device may receive a powerheadroom (PH) report at 1550 that comprises the first Type 2 PH fieldfor the primary cell and no PH field for the PUCCH SCell. If PUCCH SCellis deactivated and simultaneous PUCCH and PUSCH transmission is notconfigured for the primary cell, the eNB (base station) may receive apower headroom that does not comprise any Type 2 power headroom.

A media access control (MAC) control element (CE) comprising the PHreport may be identified by a subheader. The subheader may comprise: alogical channel identifier (LCID) field; and/or a length field. The PHreport may comprise one or more Type 1 power headroom fields. A Type 2power headroom level may be calculated employing: a PUCCH calculatedpower; and a PUSCH calculated power. A calculation of a Type 1 powerheadroom level may employ the PUSCH calculated power. The base stationmay transmit one or more power control commands employing at least a PHRMAC CE to the wireless device.

In this specification, “a” and “an” and similar phrases are to beinterpreted as “at least one” and “one or more.” In this specification,the term “may” is to be interpreted as “may, for example.” In otherwords, the term “may” is indicative that the phrase following the term“may” is an example of one of a multitude of suitable possibilities thatmay, or may not, be employed to one or more of the various embodiments.If A and B are sets and every element of A is also an element of B, A iscalled a subset of B. In this specification, only non-empty sets andsubsets are considered. For example, possible subsets of B={cell1,cell2} are: {cell1}, {cell2}, and {cell1, cell2}.

In this specification, parameters (Information elements: IEs) maycomprise one or more objects, and each of those objects may comprise oneor more other objects. For example, if parameter (IE) N comprisesparameter (IE) M, and parameter (IE) M comprises parameter (IE) K, andparameter (IE) K comprises parameter (information element) J, then, forexample, N comprises K, and N comprises J. In an example embodiment,when one or more messages comprise a plurality of parameters, it impliesthat a parameter in the plurality of parameters is in at least one ofthe one or more messages, but does not have to be in each of the one ormore messages.

Many of the elements described in the disclosed embodiments may beimplemented as modules. A module is defined here as an isolatableelement that performs a defined function and has a defined interface toother elements. The modules described in this disclosure may beimplemented in hardware, software in combination with hardware,firmware, wetware (i.e. hardware with a biological element) or acombination thereof, all of which are behaviorally equivalent. Forexample, modules may be implemented as a software routine written in acomputer language configured to be executed by a hardware machine (suchas C, C++, Fortran, Java, Basic, Matlab or the like) or amodeling/simulation program such as Simulink, Stateflow, GNU Octave, orLabVIEWMathScript. Additionally, it may be possible to implement modulesusing physical hardware that incorporates discrete or programmableanalog, digital and/or quantum hardware. Examples of programmablehardware comprise: computers, microcontrollers, microprocessors,application-specific integrated circuits (ASICs); field programmablegate arrays (FPGAs); and complex programmable logic devices (CPLDs).Computers, microcontrollers and microprocessors are programmed usinglanguages such as assembly, C, C++ or the like. FPGAs, ASICs and CPLDsare often programmed using hardware description languages (HDL) such asVHSIC hardware description language (VHDL) or Verilog that configureconnections between internal hardware modules with lesser functionalityon a programmable device. Finally, it needs to be emphasized that theabove mentioned technologies are often used in combination to achievethe result of a functional module.

The disclosure of this patent document incorporates material which issubject to copyright protection. The copyright owner has no objection tothe facsimile reproduction by anyone of the patent document or thepatent disclosure, as it appears in the Patent and Trademark Officepatent file or records, for the limited purposes required by law, butotherwise reserves all copyright rights whatsoever.

While various embodiments have been described above, it should beunderstood that they have been presented by way of example, and notlimitation. It will be apparent to persons skilled in the relevantart(s) that various changes in form and detail can be made thereinwithout departing from the spirit and scope. In fact, after reading theabove description, it will be apparent to one skilled in the relevantart(s) how to implement alternative embodiments. Thus, the presentembodiments should not be limited by any of the above describedexemplary embodiments. In particular, it should be noted that, forexample purposes, the above explanation has focused on the example(s)using FDD communication systems. However, one skilled in the art willrecognize that embodiments of the invention may also be implemented in asystem comprising one or more TDD cells (e.g. frame structure 2 and/orframe structure 3-licensed assisted access). The disclosed methods andsystems may be implemented in wireless or wireline systems. The featuresof various embodiments presented in this invention may be combined. Oneor many features (method or system) of one embodiment may be implementedin other embodiments. Only a limited number of example combinations areshown to indicate to one skilled in the art the possibility of featuresthat may be combined in various embodiments to create enhancedtransmission and reception systems and methods.

In addition, it should be understood that any figures which highlightthe functionality and advantages, are presented for example purposesonly. The disclosed architecture is sufficiently flexible andconfigurable, such that it may be utilized in ways other than thatshown. For example, the actions listed in any flowchart may bere-ordered or only optionally used in some embodiments.

Further, the purpose of the Abstract of the Disclosure is to enable theU.S. Patent and Trademark Office and the public generally, andespecially the scientists, engineers and practitioners in the art whoare not familiar with patent or legal terms or phraseology, to determinequickly from a cursory inspection the nature and essence of thetechnical disclosure of the application. The Abstract of the Disclosureis not intended to be limiting as to the scope in any way.

Finally, it is the applicant's intent that only claims that include theexpress language “means for” or “step for” be interpreted under 35U.S.C. 112, paragraph 6. Claims that do not expressly include the phrase“means for” or “step for” are not to be interpreted under 35 U.S.C. 112.

What is claimed is:
 1. A wireless device comprising: one or moreprocessors; and memory storing instructions that, when executed by theone or more processors, cause the wireless device to: receive a firstparameter indicating whether simultaneous physical uplink controlchannel (PUCCH) and physical uplink shared channel (PUSCH) transmissionis configured for a primary cell of a plurality of cells, the pluralityof cells comprising the primary cell and a PUCCH secondary cell; basedon the first parameter and the PUCCH secondary cell being deactivated,transmit a first power headroom (PH) report comprising a first Type 2 PHfield for the primary cell; and independent of the first parameter andbased on the PUCCH secondary cell being activated, transmit a second PHreport comprising a second Type 2 PH field for the primary cell.
 2. Thewireless device of claim 1, wherein the instructions, when executed bythe one or more processors, further cause the wireless device to receivea second parameter indicating that simultaneous PUCCH and PUSCHtransmission is configured for the PUCCH secondary cell (SCell),wherein: the first PH report comprises no Type 2 PH field for the PUCCHSCell; and the second PH report comprises a third Type 2 PH field forthe PUCCH SCell.
 3. The wireless device of claim 1, wherein theinstructions, when executed by the one or more processors, further causethe wireless device to receive a second parameter indicating thatsimultaneous PUCCH and PUSCH transmission is configured for the PUCCHsecondary cell (SCell), wherein the second PH report comprises a thirdType 2 PH field for the PUCCH SCell.
 4. The wireless device of claim 1,wherein the instructions, when executed by the one or more processors,further cause the wireless device to receive a second parameterindicating that simultaneous PUCCH and PUSCH transmission is notconfigured for the PUCCH secondary cell (SCell), wherein the second PHreport comprises a third Type 2 PH field for the PUCCH SCell.
 5. Thewireless device of claim 4, wherein the instructions, when executed bythe one or more processors, further cause the wireless device to receivean activation command indicating activation of the PUCCH secondary cellprior to the transmission of the second PH report.
 6. The wirelessdevice of claim 4, wherein the instructions, when executed by the one ormore processors, further cause the wireless device to: measure, by thewireless device, one or more path loss values employing signals receivedon one or more pathloss reference cells; and determine one or morefields of the first PH report employing the one or more path lossvalues.
 7. The wireless device of claim 6, wherein the instructions,when executed by the one or more processors, further cause the wirelessdevice to determine one or more fields of the second PH report employingthe one or more path loss values.
 8. The wireless device of claim 7,wherein a first media access control (MAC) control element (CE)comprising the first PH report is identified by a subheader, thesubheader comprising: a logical channel identifier (LCID) field; and alength field.
 9. The wireless device of claim 8, wherein the first PHreport comprises one or more Type 1 power headroom fields.
 10. Thewireless device of claim 4, wherein a first media access control (MAC)control element (CE) comprising the first PH report is identified by asubheader, the subheader comprising: a logical channel identifier (LCID)field; and a length field.
 11. A wireless device comprising: one or moreprocessors; and memory storing instructions that, when executed by theone or more processors, cause the wireless device to: receive a firstparameter indicating that simultaneous physical uplink control channel(PUCCH) and physical uplink shared channel (PUSCH) transmission is notconfigured for a primary cell of a plurality of cells, the plurality ofcells comprising the primary cell and a PUCCH secondary cell; and basedon the PUCCH secondary cell being activated, transmit a PH reportcomprising a first Type 2 PH field for the primary cell while thesimultaneous PUCCH and PUSCH transmission is not configured for theprimary cell.
 12. The wireless device of claim 11, further comprisingreceiving a second parameter indicating whether simultaneous PUCCH andPUSCH transmission is configured for the PUCCH secondary cell (SCell),wherein the PH report comprises a second Type 2 PH field for the PUCCHSCell.
 13. The wireless device of claim 11, wherein the instructions,when executed by the one or more processors, further cause the wirelessdevice to receive an activation command indicating activation of thePUCCH secondary cell prior to the transmission of a second PH report.14. The wireless device of claim 11, wherein the instructions, whenexecuted by the one or more processors, further cause the wirelessdevice to: measure, by the wireless device, one or more path loss valuesemploying signals received on one or more pathloss reference cells; andcalculate one or more fields of the PH report employing the one or morepath loss values.
 15. The wireless device of claim 14, wherein theinstructions, when executed by the one or more processors, further causethe wireless device to calculate one or more fields of a second PHreport employing the one or more path loss values.
 16. The wirelessdevice of claim 15, wherein a first media access control (MAC) controlelement (CE) comprising the PH report is identified by a subheader, thesubheader comprising: a logical channel identifier (LCID) field; and alength field.
 17. The wireless device of claim 16, wherein the PH reportcomprises one or more Type 1 power headroom fields.
 18. The wirelessdevice of claim 11, wherein a first media access control (MAC) controlelement (CE) comprising the PH report is identified by a subheader, thesubheader comprising: a logical channel identifier (LCID) field; and alength field.
 19. The wireless device of claim 11, wherein the PH reportis configured to be employed by a base station for at least one ofuplink packet scheduling or uplink power control.
 20. A systemcomprising: a base station comprising: one or more first processors; andfirst memory storing first instructions that, when executed by the oneor more first processors, cause the base station to transmit a firstparameter indicating whether simultaneous physical uplink controlchannel (PUCCH) and physical uplink shared channel (PUSCH) transmissionis configured for a primary cell of a plurality of cells, the pluralityof cells comprising the primary cell and a PUCCH secondary cell; and awireless device comprising: one or more second processors; and memorystoring second instructions that, when executed by the one or moresecond processors, cause the wireless device to: receive the firstparameter; based on the first parameter and the PUCCH secondary cellbeing deactivated, transmit a first power headroom (PH) reportcomprising a first Type 2 PH field for the primary cell; and independentof the first parameter and based on the PUCCH secondary cell beingactivated, transmit a second PH report comprising a second Type 2 PHfield for the primary cell.